ooRexx objects created in MSIE will have their
destructors run at the wrong time.
Speculation on: AFAIK the Rexx state is "swapped out"
whenever the border/context of a script block (ie. the
respective SCRIPT element) is left. Whenever a script
block is re-entered, the state of ooRexx is "swapped
in" and "swapped-out" again upon leaving it.
It seems that the UNINIT method gets (wrongly) invoked
at the very first time a script block is left for any
object that got created in that invocation of the
Desired resolution: only run the destructor at the time
when no more references are available to an object.