Not a red herring, just confirming it wasn't a normal application memory leak (it's not, the malloc usage is fine–I think you're hitting the same issue as is mentioned in this article). The next step I would do is run sudo footprint $(pgrep WindowServer), optionally with -v to give you a really detailed list of why the footprint is so high.