Unfortunately the split was required for other features such as Uber Jars (org.infinispan:infinispan-embedded and org.infinispan:infinispan-remote). This adds some additional work for the projects like yours, where both CDI extensions are required.
So answering your questions - yes it is safe to use both but should use so called Small Jars. If you added both org.infinispan:infinispan-embedded and org.infinispan:infinispan-remote to your deployment, you would end up with duplicated classes and in such case there are no guarantees about CDI behavior. You classpath should look like the following:
- org.infinispan:infinispan-cdi-embedded, which pulls org.infinispan:infinispan-cdi-common and org.infinispan:infinispan-core
- org.infinispan:infinispan-cdi-remote, which pulls org.infinispan:infinispan-cdi-common (already there because of cdi-embedded) and org.infinispan:infinispan-client-hotrod
I also created [ISPN-7039] Fix CDI Documentation (add information about the split) - JBoss Issue Tracker for updating documentation.