Description of problem:
When attempting to delete a bundle deployment from a destination that has multiple bundle deployments, the deletion fails if the target deployment isn't the latest. 

Version-Release number of selected component (if applicable):
3.1.2.GA

How reproducible:
Always

Steps to Reproduce:
1.  Start JBoss ON 3.1.2 system.
2.  Commit _platform_ resource to inventory.
3.  Create _compatible resource group_ that contains the _platform_ resource.
4.  Create _provisioning bundle_ using `helloworld-bundle.zip`.
5.  Deploy _helloworld-bundle_ to a destination:
    
    * *Destination Name*: `TestDestination`
    * *Resource Group*: _Platform Resources_
    * *Deployment Directory*: `/tmp/helloworld-TestDestination`
    * *Deploy Options*: _Latest Version [1.0]_

6.  Select _TestDestination_ from the _helloworld-bundle_ navigation tree.
7.  Click the _Deploy_ button:

    * *Deploy Options*: _Latest Version [1.0]_

8.  Select _Deployment [1] of Version [1.0] to [TestDestination]_ from the _helloworld-bundle_ navigation tree.
9.  From the summary panel, click the _Delete_ button.
10. Select _Yes_ when prompted to confirm deletion of the bundle deployment.

Actual results:
Message: Failed to delete the bundle deployment [Deployment [1] of Version [1.0] to [TestDestination]]

Server log contains:
    WARN  [org.hibernate.util.JDBCExceptionReporter] SQL Error: 0, SQLState: 23503
    ERROR [org.hibernate.util.JDBCExceptionReporter] Batch entry 0 delete from RHQ_BUNDLE_DEPLOYMENT where ID='10041' was aborted.  Call getNextException to see the cause.
    WARN  [org.hibernate.util.JDBCExceptionReporter] SQL Error: 0, SQLState: 23503
    ERROR [org.hibernate.util.JDBCExceptionReporter] ERROR: update or delete on table "rhq_bundle_deployment" violates foreign key constraint "rhq_bundle_deployment_replaced_bundle_deployment_id_fkey" on table "rhq_bundle_deployment"
      Detail: Key (id)=(10041) is still referenced from table "rhq_bundle_deployment".
    ERROR [org.hibernate.event.def.AbstractFlushingEventListener] Could not synchronize database state with session
    org.hibernate.exception.ConstraintViolationException: Could not execute JDBC batch update
        at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:71)
        at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43)
        at org.hibernate.jdbc.AbstractBatcher.executeBatch(AbstractBatcher.java:254)
        ...
    Caused by: java.sql.BatchUpdateException: Batch entry 0 delete from RHQ_BUNDLE_DEPLOYMENT where ID='10041' was aborted.  Call getNextException to see the cause.
        at org.postgresql.jdbc2.AbstractJdbc2Statement$BatchResultHandler.handleError(AbstractJdbc2Statement.java:2598)
        at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1836)
        at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:407)
        at org.postgresql.jdbc2.AbstractJdbc2Statement.executeBatch(AbstractJdbc2Statement.java:2737)
        ...

Expected results:
Deletion should be successful

Additional info:
It seems that the child constraint is due to the latest or live deployment referencing the previous version. This is actually true for all versions. It is like a linked list. The only deployment that doesn't reference another is the first one of the destination. What this means is that you can always delete the latest because it isn't referenced by any other deployment. However, this defeats the purpose of cleaning out the old database entries.