EAP4 used to only redeploy when a modification was made to the top level deployment descriptor. In EAP5, if any file in WEB-INF or META-INF is changed, the app will redeploy. The more aggressive behavior will likely lead to user confusion (it has to some extent in the community).

This behavior change also impacts the JBDS release, since they now need to adjust the UI to get the desired behavior.

This has been discussed in the community forum here:
http://www.jboss.org/index.html?module=bb&op=viewtopic&t=159869

The fix for this will require updates to numerous component updates in the MC including deployers, kernel, and vfs:
https://jira.jboss.org/jira/browse/JBDEPLOY-192
https://jira.jboss.org/jira/browse/JBDEPLOY-210

Due to the amount of updates required, there is no way this can make the current schedule.