First, Remember that audiences  are not, never have been and never will
be security.

Based on that there are basically two possibilities for doing what you
request. Neither is particularly easy because SharePoint doesn't make
any provision for views  to be secured, only lists and items in lists.

1) create  the views that don't filter  the library  as personal views
while logged in as the individual user. This will work, but is very
tedious.

2) Set security on the individual form  list items so that only a
group (those who should see the whole group) and the creator of the
form have access to the item. To do this going forward you will want to
create a ListItem event handler to set the security of an item when it
is inserted. This requires programming, but it's the best way to do it.

You might also want to consider an architecture change. You can create
separate libraries for the two use cases and use security at the library  level.

I found another way to accomplish what I wanted to do.

On my form library  I left only the view  that filtered to [Me] which
shows only forms  that the user submitted.

I then added a web part page and I added in the above mentioned forms
library there and was able to create  a view to see all for the
individuals that needed to see all the submitted forms and only gave
permission to them for to access that web part page.

That accomplished what I needed to do.

Just be aware that anyone who has the right to create  a page or add a
webpart can do exactly the same thing you did and see all the submitted
forms. Audiences and Views are not security.

I found a problem in that because I did not realize that even though
I had created  only one view  with filter  set to [ME] users can still
go and create  a view which will show everything.

Is there anyway to remove the Create View option from the forms
library with SharePoint Designer?

You don't need SharePoint Designer. The ability to create  a view  is a
specific permission. Create a Permission Level that has all the other
normal permissions, but not Create View. Then use that in place of
regular Contributor permissions on the Forms Library.

That is what I did. I did a copy permissions of Contributor then
down in the personal section I removed the ability to create  personal
views and created  a new permission level called formsubmitter.

I then applied the users for the library  that wer formerly
contributor this new security assignment of formsubmitter and now my
forms library is doing what I wanted.

The users can only see the views  that I have provided.

I had never drilled down into the permissions that far before and did
not see that personal section.