As stated by James F in an excellent answer at Server Fault:
The way that EV SSL certificates work is to stick an authority-specific OID in the certificate policies extension field of the cert (which is a standard X.509 certificate otherwise).
...the reference OIDs for each authority are shipped as part of the browser's root store of certificates. The user interfaces don't let you add a new CA and say "this is an EV capable CA and the UID is a.b.c.d.e.f".
I suppose it might be possible to build an open-source browser from source, adding your own CA's cert along with its EV oid to the root store, but you haven't really achieved much by doing so. The browser would no longer be compliant with the CA/Browser forum EV guidelines (which limit the EV-capable authorities).
Wikipedia has more info on EV certificates here: https://en.wikipedia.org/wiki/Extended_Validation_Certificate
Sure, this looks like a conspiracy by CAs (and browser devs). Yet, this arrangement makes for a less chaotic world.
NOTE: You can issue an EV cert with a green bar in Firefox, but you have to get a debugging build according to http://sidstamm.com/evssl-trust/firefox-evca.html
Getting others to trust your browser may be a bit difficult, though.