Well it really depends on how you define "Scenario" in your setup. To me a scenario isn't necessarily a couple test cases mashed together to form a big test case. What's the point? Haven't you already tested that?
E2E testing should encompass not only the application, but the environment. You should be testing it like a user would. E2E is about how well your software plays with others. So, in my case, when I perform this type of testing, I don't define what test cases need to be done, I define what aspects will be used. For instance, if I'm in billing, I'll hit all the parts of the application a billing person might, entering orders, printing and sending invoices, etc. However, you also have to consider externals, like our proprietary accounting system, my IM, email, etc.
So, I guess what I'm trying to say is, why would you use test cases you've already tested to death to create an end-to-end test? What are you expecting to find that you didn't already? Are you going to supply these test cases to the user so they know how they can use it? This takes a bit of thinking outside the box but, in the end, you'll probably find it's a more effective exercise then you might think.
9 out of 10 people I prove wrong agree that I'm right. The other person is my wife.