(b) Using portfolios (not really ready for that)
An ideal solution would be the ability to use variable names such as: page3.Address, page1.Address, etc.
Use hierarchal naming that includes the form and page number as part of the name, similar to the field renaming of the spawned template rename option does.
The way to go is hierarchical field names, as it has been said.
What would give you more flexibility, would be to give your element page's fields logical names. This would lead to building blocks, which can be freely combined. Any logic within the building blocks would not change at all, and logic going beyond a block would be straightforward to set up.
Hope this can help.