I'm wondering if you still see this bug in any newer stable release: it looks like we couldn't track down any reproduction of the issue at the time but 3.0 has a lot of changes since 2.3.