Probably you can override your version of JUCE news to use slot-pools for all calls of new that are the size of the message class (or something like taht). I mean Jules could probably also do that, but it might be not the best thing to do, if you are running as a DLL (e.g. you are not the host, you are being hosted) - and I believe most of the JUCE users are using it that way (e.g. some forms of VST plugins, etc.).
just my 2 cents.
I for example have local changes to my JUCE, and I do them everytime I get the latest version of JUCE, as remove any #pragma comment(lib,…) - even that you have predefined symbol DONT_INCLUDE_etc… I’m bit against that (do not like it, as I have to defined that symbol everytime I use JUCE, I don’t like much -Dxxx staying for no reason). Also juce.h never does “using namespace juce” in my local version. ZLIB/PNG/JPG are not the juce versions, but what I have on my machine, my folder. Also JUCE does not include them in my version too, but uses them externally… And few other things, but those are my local changes, and I’m not sure whether they’ll serve good purpose for the rest of the people. I do not, and do not plan to use JUCE as DLL hosted application, but rather as a separate executable - for small/medium utility tools.
What I’m saying is that if you don’t like something, you could aswell try to fix it (I’ve also fixed (kind of) one of the filler algorithms - the radial one - it was too slow, but still buggy sometimes in my version) and if Jules feels like the changes are good, he might take them, and put them in JUCE.