Using AspectJ directly and not the spring specific support for it it should work OK, this allows to develop aspects that work both in Spring and Java EE.
There are three ways to weave the AspectJ aspects into the code:
compile time weaving, meaning we need to have the code
byte code weaving can be used for third party jars for which no code is available
load time weaving (not the spring specific support) can be used to weave the aspects at class loading time, this can be more invasive as it requires a JVM wide agent, and access to the server startup script.
The spring support for LTW allows to use LTW in a more convenient way but it only works for spring applications, unlike the LTW general mechanism above.
So if using LTW directly is too cumbersome, byte code weaving and compile time weaving are still valid options, although with impact on the build process.