This issue was raised back in 2011, and Philip indicated that it would be fixed in a future release. The OP indicated some months later that the issue was fixed (but didn't say which release, comment was dated May 2011).
Could it be that this defect has crept back in? I see this still happening with 4.1.0.866.