You can "configure" the engine from within java-code as well, spring is not needed. You could use any DI-framework you want to build a process-engine configuration and build an engine from there. Start off using a "org.activiti.engine.impl.cfg.StandaloneProcessEngineConfiguration" or JTA-variant.
If you want to hook in your DI into the expressions activiti resolves, you should override the org.activiti.engine.impl.el.ExpressionManager used for this. This is a setter-method on the process-engine configuration. A good example of this is the org.activiti.spring.SpringExpressionManager, which adds an additional ELResolver for resolving spring-beans. In your case, you'll need to use your DI th get the right instance.