3289
3290 - memory leak in interactive repl

Since we switched to tracing tests in 2926 five months ago.

How would I catch this with a test, manual or automated?? I only spotted
it because I started printing num_unfreed() at the prompt.