Comment 3 for bug 628385

You are correct. I created a simplified test case to reproduce the issue we were encountering and was unable to reproduce it, so the problem must lie elsewhere in our test code. Sorry for the false alarm.