I could hook new and delete, and perhaps some other core functions, but I would rather keep the server code minimal and conflict free, so it could be an option which you have to manually enable with a define.
The gamedevwebtools::core::memory::Allocator is used internally to provide dynamic memory allocation for the server. I like the idea of setMallocCallback, setFreeCallback and the Service::malloc and free functions as they can provide an easy collection of memory stats. I'll probably add them to the next version.
Your object binding system is pretty interesting. I was thinking of adding just service method callback on certain message types, with some sort of internal mapping to map the types to the service methods. But I'll see if I can use a more powerful system.