You might be having a deployment similar to this https://issues.jboss.org/browse/AS7-1579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12622165#comment-12622165 which keeps updating some files.
The Deployment Scanner's readme file seems to suggest that any changes will trigger the redploy, per the text quoted below. This is why you can use the unix touch command to update the file's access and modification timestamps and trigger redeployment.
The filesystem deployment scanner in AS 7 and later works differently from
previous JBoss AS releases. The scanner can operate in one of two different
modes, depending on whether it will directly monitor the deployment content
in order to decide to deploy (or redeploy) it.
1) Auto-deploy mode: The scanner will directly monitor the deployment content,
automatically deploying new content and redeploying content whose timestamp
has changed. This is similiar to the behavior of previous AS releases, although
there are differences:
a) A change in any file in an exploded deployment triggers redeploy. Because
EE 6 applications do not require deployment descriptors, there is no attempt
to monitor deployment descriptors and only redeploy when a deployment
b) The scanner will place marker files in this directory as an indication of
the status of its attempts to deploy or undeploy content.
Are you using autodeployment for any specific reason? A development project? It might save you some trouble to use manual deployment and redeploy your applications with the .dodeploy marker file. Otherwise the Management Console or Management CLI is the preferred method of application management.