I ran slon through valgrind.  I didn't find any major memory leaks on
the slave slon either true memory leaks or reachable memory freed on
exit.

However, the heap usage tool showed that the slave slon was holding
onto lots of memory while running.  In fact, it was using as much
memory as was contained in the largest transaction, 53 MB in the case
of my tests.

 - Ian