Seems like this problem is fixed in trunk... might come as part of the next point release, or you may have to wait until 3.1 or 3.2 (depending on when the patch was accepted and the priority of the bug).
I can't find the bug in Bugzilla, though. My bugzilla-fu is failing me

.