@MorganBrickley
We've actually had Android export compatibility with Unity 5 for months. The problems with Unity 5 we had up until v2.2.4 were somewhat specific to Windows. Naturally that was an issue for the many developers who need to test in the Editor on Windows before exporting.
I just ran a test with Unity 5 Personal Edition to make sure this still works, and it does. Here's an updated project in yet another branch: https://github.com/leapmotion-examples/LeapMotionWidgets/tree/cardboard-vr-unity5
In another thread, Zeenobit provides some advice on configuring the plugin libraries.
I did run into a few hiccups unrelated to Leap, like having to comment out OVRTouchPad.Create(). It also has some issue where the screen turns white at certain angles, but that goes away when building a development build, and I think it's a problem with the Cardboard Unity asset which I haven't updated in a while.
Previously pro was required because leap was loading a library on android AFAIK.
That's right. With Unity 4, Pro was required to load native library plugins unless we put in some hacks. We never did attempt these Free workarounds on Android, and this didn't work too well on Windows/Mac anyhow. With Unity 5 Personal Edition, that complication goes away.