Was this ever fixed or patched in 4.1.1? We have this issue (discovered 24 hours from a major release as luck would have it!).