Description of problem:
In EAP 6, the deployment scanner will only undeploy content if it is told to do so. What this means is that if you purge a bundle all the files managed by the bundle get deleted but if any of these were actual deployments that had been deployed by the deployment scanner, they will not get undeployed. The result is that the application context may still exist or another application that may require content provided by this deployment will begin to fail because it is not aware that its dependency has been deleted.

Version-Release number of selected component (if applicable):
4.4.0.JON312GA

How reproducible:
Always

Steps to Reproduce:
1.  Install EAP 6.1 standalone server and start it.
2.  Start JBoss ON 3.1.2 system.
3.  Import EAP standalone server into JON inventory.
4.  Create a resource group containing newly imported EAP standalone resource.
5.  Create new bundle called helloworld-bundle which uses jboss-as-helloworld.war from jboss-as-quickstart:

    Recipe:
    
        <?xml version="1.0"?>
        <project name="helloworld-bundle" default="main" xmlns:rhq="antlib:org.rhq.bundle">
          <rhq:bundle name="helloworld-bundle" version="1.0" description="A sample bundle of helloworld.war from jboss-as-quickstart/helloworld">
            <rhq:deployment-unit name="helloworld" preinstallTarget="sayHello" postinstallTarget="dodeploy">
              <rhq:archive name="jboss-as-helloworld.war" exploded="true" />
            </rhq:deployment-unit>
          </rhq:bundle>
          <target name="main" />
          <target name="sayHello">
            <property name="misc.dir" value="${rhq.deploy.dir}/misc" />
            <rhq:audit status="SUCCESS" action="Preinstall Notice" info="Preinstalling to ${rhq.deploy.dir}" message="Another optional message">
              Some additional, optional details regarding
              the deployment of ${rhq.deploy.dir}
            </rhq:audit>
            <echo file="${misc.dir}/afile.txt" append="true"><![CDATA[Hello from a provisioning bundle!]]></echo>
          </target>
          <target name="dodeploy">
            <rhq:audit status="SUCCESS" action="Postinstall Notice" info="All done deploying bundle to ${rhq.deploy.dir}" message="Another optional message">
              Some additional, optional details regarding
              the deployment of ${rhq.deploy.dir}
            </rhq:audit>
            <basename property="dodeploy.filename" file="${rhq.deploy.dir}.dodeploy"/>
            <touch file="${rhq.deploy.dir}/../${dodeploy.filename}" />
            <rhq:audit status="SUCCESS" action="Postinstall Notice" info="Added ${dodeploy.filename}" message="The file ${dodeploy.filename} has been created in the directory ${rhq.deploy.dir}/.. which should trigger EAP to perform the deployment." />
          </target>
        </project>

6.  Deploy bundle to resource group using destination `helloworld.war`.
7.  Verify the application has been deployed and is available in the EAP instance.
8.  Purge the destination.

Actual results:
EAP will log a warning:

    WARN  [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 2) JBAS015006: The deployment scanner found that the content for exploded deployment helloworld.war has been deleted, but auto-deploy/undeploy for exploded deployments is not enabled and the helloworld.war.deployed marker file for this deployment has not been removed. As a result, the deployment is not being undeployed, but resources needed by the deployment may have been deleted and application errors may occur. Deleting the helloworld.war.deployed marker file to trigger undeploy is recommended.

The WAR remains deployed even though it no longer exists in the deployments directory.

Expected results:
EAP should indicate helloworld.war has been undeployed and the deployments directory should no longer contain a file named helloworld.war.deployed

Additional info:
This appears to be an overall issue in the implementation of provisioning bundles within the EAP 6 plug-in. When using the deployment scanner, we still must create meta or marker files that tell the deployment scanner what to do. These markers will depend on the application life-cycle. As you can seen in the example recipe it was necessary to create the helloworld.war.dodeploy marker file just to get the bundle to actual deploy.