Nando, you can precompile a Lucee app into a WAR and deploy it "directly" on Tomcat. Of course, the Lucee runtime is still there, there's just no CFML files. Nevertheless, here's a good book I found currently being written by someone in the community that talks a bit about how Lucee works as far as web context vs server, etc:
Habenero, if you're familiar with Java and J2EE, Lucee is a servlet that gets deployed to a servlet container of your choice. It is mapped to routes ending in .cf* and performs JIT compilation on CFML to bytecode where its loaded via a custom URL classloader inside the Lucee runtime that sits atop the J2EE runtime. Lucee's configuration tells it where your web root are, so simply modifying files there will make them picked up and re-compiled. As such, you can deploy Lucee anywhere you can run Java including Jelastic, Docker, Raspberry Pi, Win/Linux/Mac, etc. Even though most servlet containers come with an HTTP(s) listener, most people deploy it behind a web server like IIS/Apache/Ngnix to take care of static assets, SSL termination and caching. You can proxy requests to your servlet container via HTTP or AJP.
If you have more question, try to be specific. Lucee (and J2EE in general) has a lot of stuff involved :)
Thanks!
~Brad