Earlier quoted context omitted.
The point is to AOT compile to native code.
In fact that's exactly what it does: https://blog.mozilla.org/luke/2014/01/14/asm-js-aot-compilat...
In the context of that blog post, there are two compilation steps: First emscripten would be used to produce JS. Then Mozilla's JS engine would compile that JS down to machine code at runtime.
They call the latter step with OdinMonkey AOT when they compile the entire thing at runtime, but before starting execution. But the way most people differentiate, this would still be considered JIT - it still depends on executing the compiler each time the application is started.