The issue turned out to be a bug/fault in the MSA. The MSA I am using only has a single controller/storage processor and apparently regardless of if it has one or two SPs it assigns new vDisks in a round-robin fashion between the two "potential" SPs. So in my case the first vDisk was assigned to SP-A and worked beautifully. The second vDisk was assigned to SP-B even-tough it didn't exist. Therefore it was not visible to the ESXi hosts. Upon changing "ownership" of the second vDisk to SP-A the LUN was visible on the ESXi host.
Here is a link to the HP Customer Support Advisory regarding this behavior: