An Opera tech. person followed up with me on this issue and it appears that the best solution is to only execute that code for Internet Explorer--which is actually the only browser affected by memory leaks. A new release having this fix (and others) will be up in a few days.

In any case, it looks like this Opera feature is indeed implemented properly--it was our code that cleaned up, not Opera! :-) Sorry I have jumped to conclusions too fast.