Could not find anything like this in our source code, sure this is not from custom implementation?
If it can be reproduced in a plain 4.4 install and it has not been reported and fixed already then off-course create an issue so we can look into it :)