Shutting down an in-memory database is a prerequisite to deleting
it and reclaiming the memory which it occupies. In addition,
gracefully shutting down a database lets Derby reclaim the
pre-allocated but unused sequence numbers needed for explicitly
declared sequences as well as identity columns. That, in turn,
prevents Derby from leaking those pre-allocated chunks when the
database is booted next.