Creating a unique named log per connection causes memory leak

We had been experiencing a slow memory leak using postgresql-async within Play.  We tracked it down to the unique named log created when the PostgreSQLConnection is constructed.  Although the PostgreSQLConnection is destructed properly, the logging framework holds on to a reference to the logger which was created.  Overtime these build up an are never released.