As I've already captured a lot of information about this leaking MezzmoMediaServer.exe process I restarted it once it got to 1.86GB memory and 8240 file handles with the only ones that increased relating to the DB files mentioned before. Leaving it would only lead to it locking up/crashing as it exhausted its 2GB memory space.
I am disappointed that this issue doesn't appear to be of interest to the developers despite the hours effort I've gone to as per the posts above (I am a server side software dev). That leaves me with restarting the Mezzmo service every night as a workaround or just going elsewhere for music streaming.
Incidentally the product I switched to a while back for photos and videos runs on the same server and is worked a lot harder yet has stable memory and other Windows resource types. If there was any issue on the server itself then that application would be very likely to have issues as well, but it doesn't, and that's the same for the other services running.
Quick summary before I restarted the Mezzmo service:
2021-05-15_09-56-53.png
Bookmarks