JDBC LOB tests show symptoms of a leaked statement handle

The number of opens for any mxosrvr is limited to 13 due to a recent change. This exposed an issue where we were not closing some internal statements during an extract statement . JDBC driver uses the SQL extract statment to implement the stream API. This exposed the issue.
The test failed with this error:

> 2017-08-16 01:12:27 Running testBatchInsertFKNotExist......
> 2017-08-16 01:12:56 Batch Update Failed, See next exception for
> details
> 2017-08-16 01:12:56 *** ERROR[8103] The operation is prevented by
> referential integrity constraint
> TRAFODION.T4QA.BATCH_TEST_TABLE_FK_911645628_4551 on table
> TRAFODION.T4QA.BATCH_TEST_TABLE_FK.
> 2017-08-16 01:13:11 *** ERROR[2026] Server Process $ZSM0 has reached
> allowed depth for nowait operation from the process 0,15846.
> [2017-08-16 01:13:11]
>

Debugging and dumping hte open and fetch statements in the context at that point showed this pattern :

There were around 13 statements in OPEN or FETCH statement with the
> source string "select dataOffset, chunkLen, stringParam from
> table(ghost table
> "TRAFODION"."T4QA"."LOBDescChunks__08574991311373262837_0002")
> where descPartnKey = and descSyskey = "
>
> These internal statements should be closed for the jdbc_test_cdh to
> pass or comment out the tests that triggers these internal statements
> for time being.