While no specific code fix was supplied for this issue, the issue could not be duplicated after upgrading to 4.0, service pack 4.  We'd suggest applying the latest service pack and/or hotfix if this issue is experienced on a version prior to 4.0, Service Pack 4.