> >> Since statement closing is quite good idea :),
> >> result set will be usually closed earlier.
>
> Yes, but sadly I cache my statements across transactions since I
> have a finite number of them and they are so much faster once
> prepared.

Then you should close result set when you return statement to the pool.

If you wish, you can try org.firebirdsql.pool.* classes that provide
you transparent prepared statement caching, i.e. you can close
statement after each execution and it will be still fast.

Roman