I reported this via a support request and it was (finally) acknowledged as a bug. It took a while because the development team could not reproduce the problem (and in fact, it was only happening on one of my systems).
There is a technical review version available which fixes most of the problem but there are still some issues that have been acknowledged as needing to be fixed. I am told that the complete fix should be in the next release and may appear in a technical review, beta, or release candidate release prior to that.
I would suggest that you also open a support request for this issue.