The browser process (IE) is not releasing Memory when an Applet is destroyed.
To reproduce the problem, open up IE. Click on File - New Window. (Both windows are now running under one IE process) In the first window, load a
simple applet which uses the plugin and minimize it. Note the size of the 'Private Bytes' of the IE process in the Performance Monitor using the Report Data view. In the second window, load a larger applet and interact with it.
You should note an increase of the 'Private Bytes' of the process. Now close
the second window. You should notice that memory is not released even though
the second applet has been destroyed.

To reproduce the bug, please see the attached test case and instructions included in the Comments section.