[BUG] /v1/sessions/:sessionId/release endpoint does not work with recent images

[LitPrompt]

Describe the bug
The /v1/sessions/:sessionId/release endpoint does not work as expected. Calling the release method on this path has no effect and the session is not released successfully.

To Reproduce
Steps to reproduce the behavior:

1. Create a session using the latest image.
2. Interact with the session to generate some context.
3. Call the /v1/sessions/:sessionId/release endpoint for this session.
4. Use return sessionId for the new session call the /v1/sessions/:sessionId/context.
5. Observe that the returned data is still the context from the previously released session, showing it was not successfully cleared.

Expected behavior
After calling the /v1/sessions/:sessionId/release endpoint, the session context should be fully released and cleared.
A newly created session should start with a clean context and should not contain any data from previously released sessions.

Screenshots

Desktop (please complete the following information):

• OS: Ubuntu 22.04
• Browser N/A
• Version N/A

Smartphone (please complete the following information):

• Device: N/A
• OS: N/A
• Browser N/A
• Version N/A

Additional context
The issue seems to be image-version related. Sessions created with images dated 2025-09-11 correctly release and isolate context, while sessions created with newer images do not fully clear context after calling the release endpoint.

[jhstatewide]

This makes it pretty challenging to use the published Docker image... is there any chance of getting version tagged images published? Always using :latest is tough because of situations like this.