Currently, the share-prepared-statements detail leaves developers with the impression they do not need to close statements in their code:

Whether asking for the same statement twice without closing it uses the same underlying prepared statement.

Instead, the omitted closure that permits reuse/sharing is within the underlying EAP pooling implementation (something the developer doesn't directly control). Failure of the developer's code to close statement references will actually prevent sharing rather than permitting it (and this can lead to rapid memory growth).

The documentation should say something along the lines of:

Whether EAP should cache the underlying physical statement (rather than closing/terminating it) when the wrapper supplied to the application is closed by application code.