This bug can be considered an independent task or as an action item for the future development work. XPConnected plugins need some special treatment when we decide to shut them down and unload their dlls from memory. XPCOM may have outstanding references to the plugin scriptable object and currently we don't have a reliable way to determine when all plugin related ref counts get down to zero and the dll can be unloaded. I think there can be different approaches to address the issue, we can probably briefly exchange ideas here.
reassigning to myself
Only unload these plugins when XPCOM broadcasts the shutdown notification. Also we need to ensure that developers of these plugins get the message that after this notification all outstanding refereces to mozilla are invalid.
moving to 1.3 beta, this should get resolved for 1.3
--->taking av's nsbeta1+ bugs
Target milestone should be changed, mozilla1.3beta was a long time ago.