yes, please take the newest xmlBlaster from svn, this simplifies it for us.
Could you then please start xmlBlaster in a tool like OptimizeIt and see if/how your use case produces leaks?
All right, it's been running for some time now, no problems... will run it through a mem profiler if it pops up again. Maybe under heavier load, but hopefully not. :)