Derby v. Memory

It seems like calling getConnection with a connect string that ended in ";shutdown=true" is a good way to get Derby to leak lots of memory. But only when running in Tomcat (on Solaris, if that's relevant). Calling getConnection to shut down Derby also takes about a second, which really adds up if you're trying to shut down Derby after every DB call, as I was.