assorted memory leak cleanups

tidy up a few stray memory allocations.  Is there a better way to deal
with HumanReadable than to point to a statically allocated global array?