We have confirmed that the issue exists in version 4.0.2a, however, it appears to have been resolved by engineering in our most recent development branch. It should be included as part of our next maintenance release.