Hmm... I'm going to have to assume this is the result of a bad upgrade, or an outdated build... I don't see this in the latest build at all. We did make some changes to the header code in a recent build so I could definitely see it being an upgrade issue.