So that is a small lie.. It no longer works in about half of my settings.. all that was changed was updating to 3.33a.. dont remember last version i had but i believe it was the most current pub release.

There is no known issue with #T- or #T+. What is probably happening is that you are having multiple operations occur on the same target entity (ie, trigger A fires and uses #T- on some class and then Trigger B fires and uses #T+ to re-enable it.

I've encountered a problem with #T- or #T+.
They didn't work in little-more-than-simple zScripts. In order to make them work I had to move them out of those little-more-than-simple zScripts.
(The scenario of Matt doesn't happen in my case; I have a linear firing of triggers; As I said, moving the #T-/+ in another script works)
I didn't have the time to study this in more depth and report a bug since I circumvented the issue by moving the #T-/+ in simpler scripts.

Sorry for not having hard evidence for this, but, when I'll have the time, I'll produce a test case and present it here.

Agree all you want, there really is no issue with it. You either are seeing something similar to what I described (the scripts don't even have to be related in any way other than that they operate on the same setting), or you are affected by data corruption.