Exchange 2010 CAS Array, do you really need it?

I've encountered a number of deployments of Exchange 2010 that are not using/configuring CAS Array prior to creating mail databases (and it's a mess in terms of troubleshooting); even a number of "deployers" doesn't even know what CAS Array is! There is also confusion that CAS Array is also the NLB!  I hope upon reading this you will be enlightened:

1. NLB (Network Load Balancing)  is different from CAS Array; as explained in Microsoft's Technet Article:

"A Client Access server array doesn’t provide load balancing. A separate load balancing solution is still needed" http://technet.microsoft.com/en-us/library/ee332317.aspx#CASarray

2. What if you only have a single, multiple Exchange Role Server? Do you still need to configure a CAS Array?

"We recommend that you create a Client Access server array even if you only have a single Client Access server within your organization"
http://technet.microsoft.com/en-us/library/ee332317.aspx#CASarray

and as explained further:
"When a Client Access server array is created, clients connect through the virtual name of the Client Access server array rather than directly to the fully-qualified domain name (FQDN) of your single Client Access server. If a single Client Access server needs to be replaced within an Active Directory site or a second Client Access server is added, no profile updates are necessary on the clients."

This can help you ease things out especially if there will come a time that you need to replace your CAS server or if you will add another CAS server.

3. Another question that was asked: Is autodiscover the same as the CAS Array?
As stated above, clients will connect through the virtual name (CAS Array name) instead of the FQDN of the server; e.g. Upon setting up Outlook client to connect to the Exchange Server, it will automatically detect a "name", you will notice that it will show the CAS Array name instead of the FQDN of the CAS Exchange Servers (and this process is called "Autodiscover")