Nope. Ears aren't bean archives (they can't directly contain bean classes). So it doesn't make sense to put beans.xml directly in the ear. A war is a bean archive.
OTOH, having a beans.xml on EAR level for application wide config (interceptors, alternatives) wouldn't perhaps be a bad idea but then the rules would have to propagate down the archive hierarchy (EAR -> WAR, EAR -> JAR)