Has anyone else seen this happen before?
Thanks for the replies all, we figured out why this is happening and are fixing it in an upcoming patch (not 5.2).