Hi masspeaceaction: this does indeed look like a bug and we probably should be doing pretty much as Andy suggested to avoid this. We’ll get it on the tracker and sort something out over the course of the next few releases.
Thanks for reporting (and thanks for your help, Andy) 🙂
I just wanted to pop in here with a quick update. Although we were not able to get a fix for this into our imminent 3.3 release, it is still on the radar for inclusion in a future build. Thanks for your patience!
I’m happy to report that we have fixed this in our upcoming version 3.4. Keep an eye on your Plugins page for an update message! Thanks for your patience while we worked on this.