Hi Rick,
We encountered the same problem on Linux. What we found was the
following.

In our code we created resultsets like this:

rs = connection.createStatement().executeQuery("select ...");
...
rs.close();

We were reusing connections using an in-house connection pool.
What is boils down to is the connection retains a link to the
statement object which has not been closed.

If you close the connection or add a

rs.getStatement().close();

before the rs.close your problems should stop.

Regards
Ian Newby