What is the reason that EJB 1.0 was considered a failure?

During the DOT COM Boom of the late 90's and Early 2000's lots of consultants made money selling Enterprise Java solutions. Yet 5, 10 and 15 years later, any mention of 'EJB' gets a scowl and a scoffing remark in response.

As I understand it (and I could be oversimplifying things), EJB was an attempt at standards for distributed components, with a persistence standard, transaction standard and over-the-wire communication in Java.

The particular flaws of EJB 1.0 appear to be:

• complexity of the standard
• poor persistence implementation
• unnecessary usage of patterns
• poor performance for low-scale scenarios
• an overuse of a solution that was aimed at a very narrow set of scenarios (big companies writing big monolithic solutions with large teams)

My question is: What is the reason that EJB 1.0 was considered a failure?

(This question is becoming more important now with the rise of microservices which follows a very similar model).