I am also running 3.6 on a couple of production sites and I had the exact same problem as you have described.

However, since the last update (to 3.6-beta4) this problem is no longer.