I apologize for not having more time to look in to the following, but thought I'd mention a copule of glitches as a heads up -
(1) The "post" that a soundfont is loaded actually only happens for the _first_ soundfont loaded. I remember this from a while back, it's a bug in how fluid~ is interpreting a return value from some fluid function - don't remember the details now.
(2) The following sequence hogs my machine: instantiate fluid~ , load a large soundfont, close the fluid~ patch, instantiate fluid~, load a large soundfont. I checked, and the appropriate fluid API function _is_ being called on deletion. Sure seems as if my soundfont isn't getting back to the free store somehow (it's about 50% of my RAM).
Larry