This problem still exists even in 3.0.12. I see people have filed a few bugs about this but the issue still exists. This is the only reason I have been using 3.0.4 for the past while. Considering something was broken by an update, hopefully it's not that difficult to fix in a timely manner.