IMO
EA's "view" is a (UML) model organization construct representing a (top level) collection point for some, user/usergroup defined, way of looking at the System. I, for example, use 4 primary views loosely aligned to the RUP structurals. Mine are "Requirements" view, "Analysis" view, "Design" view and "Deployment" view. Others might use CIM, PIM, PSM views. Its all horses for courses.
UML "models", in my interpretation, are a complete specification of a physical system from some particular aspect - maybe structural, maybe behavioral for instance. A System may be composed of more than one system.
Adding a view in EA adds just the top level package element whereas adding a model firstly adds a (complete) prototype of a UML model - including substructures and occassionally sample elements. Secondly, I believe that a model could/can be added at subsequent levels of the repository organizational heirarchy, depending n the needs of the analysts/designers.
So I actually find the terminology consistent.
bruce