connection pooling and open statement objects

hi,

 In an earlier discussion, someone had remarked that if the statment
objects are not explicitly closed, the resources allocated to it are not
released. ie,  I have code like this:

 - get Connection object from connection pool
 - create statement object
 - create resultset using the statement
 - process the resultset
 - return the connection object to the connection pool

 This cycle is repeated for all the sql statements in the application. If
the
memory will not be released till the statement object is explicitly closed,
then it
might lead to a memory leak later.

any suggestion or remarks are welcome

regards,
Nagarajan.