Slimming down a deployment on WildFly

Vaadin 6 / 7 / 8
1

I’m looking at a way of slimming down our Vaadin-deployments on the WildFly AS. When I look at the libs included currently I see

31.03.2017  12.03           254 911 deltaspike-core-api-1.7.2.jar
31.03.2017  12.03           151 854 deltaspike-core-impl-1.7.2.jar
25.01.2017  13.22            79 797 flute-1.3.0.gg2.jar
02.03.2017  09.57            23 161 gentyref-1.2.0.jar
25.01.2017  13.17            55 784 jackson-annotations-2.8.0.jar
25.01.2017  13.17           280 014 jackson-core-2.8.1.jar
25.01.2017  13.17         1 230 290 jackson-databind-2.8.1.jar
25.01.2017  13.17            30 225 jackson-jaxrs-base-2.8.1.jar
25.01.2017  13.17            15 805 jackson-jaxrs-json-provider-2.8.1.jar
25.01.2017  13.17            34 554 jackson-module-jaxb-annotations-2.8.1.jar
25.01.2017  13.22           315 320 jsoup-1.8.3.jar
25.01.2017  13.22            15 808 sac-1.3.jar
31.03.2017  12.03            64 526 vaadin-cdi-2.0.0.jar
24.03.2017  11.10           763 637 vaadin-client-compiled-8.0.4.jar
25.01.2017  13.22           532 600 vaadin-sass-compiler-0.9.13.jar
24.03.2017  11.10         2 373 009 vaadin-server-8.0.4.jar
24.03.2017  11.10           441 003 vaadin-shared-8.0.4.jar
24.03.2017  11.10         6 578 860 vaadin-themes-8.0.4.jar

Has anyone tried moving all vaadin.jars to a WildFly module? The AS has the jackson-stuff for 2.7.4 so the module could probably use those(?). The deltaspike came with the cdi-integration but those aren’t probably hard-linked?