Thanks for the note. As I mentioned in your other post this is actually a known bug (also reported here). We are working on getting it fixed, so it should be corrected in the next maintenance release. I apologize for the inconvenience in the meantime.