asp.net - Recommendation for Viewstate abuse -

I was going through a list of Scott's NAT questions

There is a scenario in a comment - You are reviewing an asp.net application and can find out that the viewsto is storing "ID", which is being used on different pages for different unrelated purposes. Maybe productID for one page in personID, other pages etc.

What will be your recommendation?

I do not see this problem. Each page, and therefore each viewest instance, is a different reference. One page of the viewest item has no relation to the viewstate item in another page, so there is no chance of confusing them. The nature of 'id' should be clear, when code the page - this is an individual ID, product ID, customer ID or whatever.