[maxmsp] Possible memory leak in mxj network objects?

In the process of figuring out why one of my patches keeps crashing (which I believe to be a regexp issue...more on that in another post), I noticed something with the memory usage of Max while sending data to the mxj net.multi* objects: memory kept increasing, and after closing the patch, was never released (the memory needed for the patch was, but the increase due to sending data to the net.multi* objects remains. I did a little test and noticed this was true of all the net* ojects, but didn't see this using the udpsend/reveive object. Run the patch long enough and I get a crash, showing 300+ threads, most of which appear related to JVM. 

Below is a patch to help illustrate this, and attached is my most recent crash report.

max v2;
#N vpatcher 4 44 1169 476;
#P origin 11 21;
#P window setfont "Sans Serif" 9.;
#P newex 906 265 86 196617 udpreceive 4444;
#P newex 906 235 120 196617 udpsend 127.0.0.1 4444;
#P newex 639 269 143 196617 mxj net.tcp.recv @port 7778;
#P newex 639 235 261 196617 mxj net.tcp.send @address 127.0.0.1 @port 7778;
#P user ubumenu 154 155 100 196617 0 1 1 0;
#X add don't send;
#X add mxj broadcast;
#X add mxj UDP;
#X add mxj TCP;
#X add udpsend;
#X prefix_set 0 0 <none> 0;
#P newex 154 201 143 196617 gate 4 0;
#P newex 400 269 144 196617 mxj net.udp.recv @port 7777;
#P newex 400 235 235 196617 mxj net.udp.send @address 127.0.0.1 @port 7777;
#P window linecount 6;
#P message 287 115 345 196617 <sqparams loadsound = '1 0. 0. shotgun breech.aif' playsound = '1' speed = '1.000000' loop = ' 0 ' sfvolume = ' 0. ' speakerset = '1' az-ch1 = ' 30. ' local-ch1 = ' 30 ' az-ch2 = ' -30. ' local-ch2 = ' 30 ' releasewithstop = '1' releasewithvol = '0' sync = ' 0 ' ubervolume = '-90.' ubervolume = ' -9. 10 0.5 ' play = '1' retrigger = '2' destination = 'fred' type = 'newvoice' triggeredby = '201' subcueidentifier = 'shotgunbreech'/sqparams>;
#P toggle 287 70 15 0;
#P window linecount 1;
#P newex 287 91 46 196617 metro 5;
#P newex 154 269 242 196617 mxj net.multi.recv @group 224.0.1.20 @port 7474;
#P newex 154 235 241 196617 mxj net.multi.send @group 224.0.1.20 @port 7474;
#P window linecount 3;
#P comment 384 321 329 196617 Watch memory usage in the activity monitor (if on a mac). all the mxj network objects continue to take up memory \, and never release it when you close the patch. The non-mxj udp object works are expected.;
#P window linecount 1;
#P comment 132 135 141 196617 select type of communication;
#P connect 10 0 9 0;
#P connect 9 0 2 0;
#P connect 5 0 4 0;
#P connect 4 0 6 0;
#P connect 6 0 9 1;
#P fasten 9 1 7 0 203 232 405 232;
#P fasten 9 2 11 0 247 229 644 229;
#P fasten 9 3 13 0 291 226 911 226;
#P pop;

-------------- next part --------------
A non-text attachment was scrubbed...
Name: crashreport.rtf.zip
Type: application/zip
Size: 12273 bytes
Desc: not available
Url : http://www.cycling74.com/pipermail/maxmsp/attachments/20070710/2e8e86bf/crashreport.rtf.zip