looks like it's related to the transaction last resource optimization in two-phase commit. Can you check the datasource configuration in WildFly or EAP configuration file (standalone.xml or domain.xml), and try setting it to <xa-datasource> (you might have used <datasource>). Aside from the warning message, does it affect your application any other way?
if your batch application does not need global transaction (e.g., item reader), you can configure the datasource to be non-jta. That may exclude it from being enlisted by the transaction manager.