Leak in client if ResultSet not closed

If I run the attached program RepeatStatement.java with 32M of heap,
I will get an OutOfMemory error in the client.

java -Xmx32M RepeatStatement
Exception in thread "main" java.lang.OutOfMemoryError: Java heap space
at org.apache.derby.client.am.Cursor.allocateCharBuffer(Cursor.java:1260)
at org.apache.derby.client.net.NetStatementReply.parseSQLDTARDarray(NetStatementReply.java:1356)
at org.apache.derby.client.net.NetStatementReply.parseQRYDSC(NetStatementReply.java:1207)
at org.apache.derby.client.net.NetStatementReply.parseOpenQuery(NetStatementReply.java:479)
at org.apache.derby.client.net.NetStatementReply.parseOPNQRYreply(NetStatementReply.java:223)
at org.apache.derby.client.net.NetStatementReply.readOpenQuery(NetStatementReply.java:64)
at org.apache.derby.client.net.StatementReply.readOpenQuery(StatementReply.java:50)
at org.apache.derby.client.net.NetStatement.readOpenQuery_(NetStatement.java:153)
at org.apache.derby.client.am.Statement.readOpenQuery(Statement.java:1396)
at org.apache.derby.client.am.Statement.flowExecute(Statement.java:2001)
at org.apache.derby.client.am.Statement.executeQueryX(Statement.java:421)
at org.apache.derby.client.am.Statement.executeQuery(Statement.java:406)
at RepeatStatement.testInsertAndSelect(RepeatStatement.java:31)
at RepeatStatement.main(RepeatStatement.java:10)

If I close the ResultSet or Statement it does not leak.

This occurs on trunk and 10.2.1.6. It does however not run out of memory on 10.1.3.1, so appears to be a regression.