BackingBeanScope and dynamic regions

Question

I have a clarifying question about BackingBeanScope. Here's the scenario... I have a dynamic region. In that region I can render either flow 1 or flow 2. The page in flow 1 has an af:inputText component with a component binding in BackingBeanScope. It looks something like this #{backingBeanScope.id}. The page in flow 2 also has an af:inputText component with a component binding in BackingBeanScope - #{backingBeanScope.id}. This is where I found the surprising BackingBeanScope behavior. In my dynamic region, I enter a value in flow 1's inputText then navigate from flow 1 to flow 2, the value in flow 1's inputText gets applied to flow 2's inputText.
Here's what is happening. After I enter a value in flow 1's input text and click the button to navigate to flow 2, the value gets stored in BackingBeanScope during the RESTORE_VIEW phase of the request. During the RENDER_RESPONSE phase of the the same request, the value that was previously stored on the BackingBeanScope get pulled off and applied to the inputText of flow 2. This is because the BackingBeanScope is tied to the dynamic region (using the region as the ID for the scope).
With this discovery, is it reasonable to conclude that the following two rules are best practices?
1) All EL that uses backing bean scope must be unique across the application
2) All beans that are in backing bean scope must have unique names.
Cheers,
Mike

Answer 1

I created two sample applications. One of them demonstrates the EL collision. The other one demos the managed bean collision.
[url http://dl.dropbox.com/u/6316698/BackingBeanBug-ELCollision.zip]EL Collision Sample App
To run:
- Extract zip file
- Right click Main.jspx-->Debug
- In the App, click Flow 1.
- Type in a value and click Flow 2
- Notice that the value stayed the same, but the flow changed to "Flow 2".
[url http://dl.dropbox.com/u/6316698/BackingBeanBug-ManagedBeanCollision.zip]Managed Bean Collision Sample App
To run:
- Extract zip file
- Right click Main.jspx-->Debug
- In the App, click Flow 1. Notice that it says "Page 1BackingBean1".
- Type in a value and click Flow 2
- Notice that the value stayed the same, but the page changed to "Page 2". However, it is still referencing BackingBean1 (from the previous flow)