The behaviour that you described is expected, because by design when server paging is used the DataSource keeps only the records of the current page. In other words when the second page is loaded, the data of the previous (first) page is replaced. As a result the old ListView items persists in the html mark-up but their corresponding dataItems are not stored in the DataSource.
This is done for performance reasons - assuming that the scroll is endless, keeping all dataSource pages may cause memory issues.
The behaviour cannot be prevented, however there is an easy way to use the ListView items as navigation links. The html mark-up of previous items is not cleared so you could render the items as links and use them to change the Views. Also it is possible to store additional data (such as the item's ID) in the mark-up as custom data attributes and retrieve it later at the click event.
As the old dataItem does not persists in the DataSource, I suggest to issue another Ajax call to the server to retrieve it. As the success event of that request, you can update the ViewModel and navigate to the details View.
the Telerik team
Join us on our journey to create the world's most complete HTML 5 UI Framework - download Kendo UI