#6 - Oct. 28, 2010, 3:20 a.m.
So, I do have some news on this one. It looks like this issue was already made known to us, is being addressed, and we are looking to hopefully resolve the issue in an upcoming patch. Unfortunately I am unable to provide more specifics, but I do hope that helps to set your minds at ease. >^.^<