You're actualy talking about caching for different instances of a page.
That's an issue you should solve by design.
You have many different ways you must consider according to the nature of
your application.

Normaly the place to hold a page instance specicifc data should be the view
state. If you'll save that in the view state there won't be any chance that
the data will be overriden in another instance.
One reason not to do that would be large size of data and small bandwith.
You can solve that by compressing the view state for example.
Though, if the data is too large for view state it might be too large for
the session as well.
What you should consider then is using paging through the SQL server
instead.