Description of problem:
[root@sgi-xe310-02 ~]# rpm -qa | grep aeolus
aeolus-conductor-0.3.0-0.el6.20110708135911gitdb1097c.noarch
rubygem-aeolus-cli-0.0.1-1.el6.20110708135911gitdb1097c.noarch
aeolus-all-0.3.0-0.el6.20110708135911gitdb1097c.noarch
aeolus-configure-2.0.1-0.el6.20110707131907gitfaa220b.noarch
aeolus-conductor-doc-0.3.0-0.el6.20110708135911gitdb1097c.noarch
aeolus-conductor-daemons-0.3.0-0.el6.20110708135911gitdb1097c.noarch


recreated this again.. I was hoping it was a fluke w/ my system.
recreate

1. setup conductor, and start a deployable in the default pool
2. create a new pool in the default pool family
3. expand the new pool or go to list view

Notice the original deployment is also listed in the new pool.

I spoke w/ Hugh about it, just to make sure that was not some design that I was unfamiliar w/. 

The bug is fixed when you create a new pool and it does not mirror deployments from other pools.